Manuel star do/release/v20.1.0#669
Conversation
* feat: add nau basic customization * fix: remove unnecessary courseOrg as argument
* fix: platform logo on mobile display * fix: hide course name on mobile
Rename the setting to be in the present tense, as a way to make it clearer. The setting is now called `ENABLE_ORG_LOGO`.
- remove the semantic release code and replace it with JS-Devtools
Add max width for org logos, there are logos too wide. Increase course name to full width, it hides if not has available space. Show language select compacted version on 1200 width.
fix: only get org logo if user is authenticated fccn/nau-technical#411 fix: header language selector fccn/nau-technical#412
fix: call organization API if user is authenticated Only call Organization API if the user is authenticated. With this fix when the user isn't authenticated, it won't raise an error when calling the API. If something strange happens it will log it, but it won't crash the Microfrontend. fccn/nau-technical#411
Always use the compacted version of the language selection on the header. When Richie changes the language cookie to be 'pt' the MFEs show any language on the header, so it is kind of strange. So now showing the language name on the header is better, it hides the problem and give us more space on the header, but still showning an easy way the learner to change it.
Add a new flexbox rule to guarantee correct separation of components. Create a new container for the right elements.
Fix an issue with the header where the items wouldn't align properly on mobile. Always use the compact version of the language select to improve the flow of the header.
Fix header logo height size
Generate Teak initial release
adds missing import and renders LearningHelpSlot inside the authenticated user block to support plugin injection
openedx-webhooks
added
the
open-source-contribution
|
Thanks for the pull request, @ManuelStarDo! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Submit a signed contributor agreement (CLA)
If you've signed an agreement in the past, you may need to re-sign. Once you've signed the CLA, please allow 1 business day for it to be processed. 🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
7 participants
Release version to deploy PR #26
Adds a missing import and renders just before inside the authenticated user block, matching the position used in the upstream header.